-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix resolve_delayed #1006
fix resolve_delayed #1006
Conversation
Code Coverage Summary
Diff against main
Results for commit: 6f911b0 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Reviewed and tested the sample app code and run it without any issue in both the main and current branch. 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per discussion with @gogonzo the refactoring of teal.transform
is on the horizon, teal.transform
isn't handled by teal at all and the role it will play in aiding module development.keeping it in vignettes now will force us to add it to suggests in teal , After refactor if required this will be to added it to teal documentation.
part of insightsengineering/teal.transform#111
resolve_delayed
has been fixed on the feature branch inteal.transform
and it is not needed anymore inteal
as (delayed)data_extract_spec
are resolved in data_extract_single_srv when module is initialized. This means that resolve_delayed doesn't have to be imported inteal
.resolve_delayed
is the onlyteal.transform
function used inteal
, soteal.transform
is removed from the dependencies. I support this move becauseteal.transform
is used only by some modulesteal.modules.general
,teal.modules.clinical
,teal.goshawk
.very, very, very long app code
App contains different
data_extract
configurations includingdelayed_
- app is to prove that they are resolved even when removed from teal. Each module should have the same output on thisbranch
and onmain